Fixes #9908

Addresses an issue raised as a priority by some of our embedded users, like gcloud & Cloud Code. For both providing more useful feedback to the user, and collecting statistics about why minikube fails in user environments.

Split one broad code into 12 codes. I suspect many of these will be rarer than hens teeth, but I've sorted by intuitional likelihood:

• PROVIDER_DOCKER_WINDOWS_CONTAINERS
• PROVIDER_DOCKER_DEADLINE_EXCEEDED
• PROVIDER_DOCKER_INFO_FAILED
• PROVIDER_DOCKER_INFO_ERROR
• PROVIDER_DOCKER_VERSION_EXIT_%d
• PROVIDER_DOCKER_NEWGRP
• PROVIDER_DOCKER_NOT_RUNNING
• PROVIDER_DOCKER_PIPE_NOT_FOUND
• PROVIDER_DOCKER_CANNOT_CONNECT
• PROVIDER_DOCKER_REFUSED
• PROVIDER_DOCKER_ERROR

Here are some examples I forced:

docker version with exit code 9

😄  minikube v1.16.0 on Darwin 11.1 (arm64)
✨  Using the docker driver based on user configuration

💣  Exiting due to PROVIDER_DOCKER_VERSION_EXIT_9: "docker version --format -" exit status 9: 
📘  Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/

docker not running

😄  minikube v1.16.0 on Darwin 11.1 (arm64)
✨  Using the docker driver based on user configuration

💣  Exiting due to PROVIDER_DOCKER_NOT_RUNNING: docker info error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
💡  Suggestion: Start the Docker service
📘  Documentation: https://minikube.sigs.k8s.io/docs/drivers/docker/